Compare Page

Data punctuality

Characteristic Name: Data punctuality
Dimension: Availability and Accessability
Description: Data should be available at the time of its intended use
Granularity: Information object
Implementation Type: Process-based approach
Characteristic Type: Usage

Verification Metric:

The number of tasks failed or under performed due to lack of data punctuality
The number of complaints received due to lack of data punctuality

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Standardise the timelines for the availability of information for a particular task (1) Investment product pricing data is often provided by third-party vendors. As the success of the business depends on accessibility to that pricing data, service levels specifying how quickly the data must be provided are defined and compliance with those timeliness constraints.
Create efficient processes for information delivery by removing the bottlenecks in information flow (1) Billing details of a patient is gathered two hours before discharging the patient

Validation Metric:

How mature is the process of ensuring data punctuality

These are examples of how the characteristic might occur in a database.

Example: Source:
1) For example, the best and easiest method to obtain demographic information may be to obtain it from an existing system. Another method may be to assign data collection by the expertise of each team member. For example, the admission staff collects demographic data, the nursing staff collects symptoms, and the HIM staff assigns codes. Team members should be assigned accordingly.

2) For example, patient census is needed daily to provide sufficient day-to-day operations staffing, such as nursing and food service. How- ever, annual or monthly patient census data are needed for the facilityís strategic planning.

B. Cassidy, et al., “Practice Brief: Data Quality Management Model” in Journal of AHIMA, 1998, 69(6).

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
1) The characteristic of getting or having the Information when needed by a process or Knowledge Worker.

2) The Characteristic of the Information being accessible when it is needed.

ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
Is the information processed and delivered rapidly without delays? EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer.
Timeliness refers to the time expectation for accessibility and availability of information. Timeliness can be measured as the time between when information is expected and when it is readily available for use. For example, in the financial industry, investment product pricing data is often provided by third-party vendors. As the success of the business depends on accessibility to that pricing data, service levels specifying how quickly the data must be provided can be defined and compliance with those timeliness constraints can be measured. LOSHIN, D. 2006. Monitoring Data quality Performance using Data Quality Metrics. Informatica Corporation.
Timeliness reflects the length of time between availability and the event or phenomenon described. Punctuality refers to the time lag between the release date of data and the target date when it should have been delivered. LYON, M. 2008. Assessing Data Quality ,
Monetary and Financial Statistics.
Bank of England. http://www.bankofengland.co.uk/
statistics/Documents/ms/articles/art1mar08.pdf.

 

Redundancy

Characteristic Name: Redundancy
Dimension: Consistency
Description: The data is recorded in exactly one place
Granularity: Record
Implementation Type: Rule-based approach
Characteristic Type: Declarative

Verification Metric:

The volume of redundant data as a percentage to total data

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Maintain the database schema eliminating the causes for redundancies of entities and attributes (1) All customers are in customer table
Ensure that there are no redundant records across distributed databases (1) Organisation has different customer bases maintained in different databases. But one customer is available only in one database
Ensure that same entity is not originally captured more than once in the systems (1) Medical Insurance system refers employee bank details from the payroll.
Ensure that there are no temporary table backups are available in the database (1) Created a backup for employees as employee_temp for a specific purpose and it is still in the database

Validation Metric:

How mature is the creation and implementation of the DQ rules to eliminate the occurrence of redundant data

These are examples of how the characteristic might occur in a database.

Example: Source:
A school has 120 current students and 380 former students (i.e. 500 in total) however; the Student database shows 520 different student records. This could include Fred Smith and Freddy Smith as separate records, despite there only being one student at the school named Fred Smith. This indicates a uniqueness of 500/520 x 100 = 96.2% N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
A measure of unwanted duplication existing within or across systems for a particular field, record, or data set. D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
There is only one record in a given data store that represents a Single Real-World Object or Event. ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
Determines the extent to which the columns are not repeated. G. GATLING, C. B., R. CHAMPLIN, H. STEFANI, G. WEIGEL 2007. Enterprise Information Management with SAP, Boston, Galileo Press Inc.